Description of your changes

As detailed in the linked issue, the post release workflow was not working as intended. Due to this, the comment that was left under the issues related to a release did not include the correct release number. This caused the maintainers to have to manually fix all the comments after each release.

This PR introduces a new step to the post-release workflow that checks the presence of the release version, and if it's not present in the inputs (which is the case when the workflow is triggered by a release), it retrieves it from the latest git tag.

This should fix the workflow and make it so that the comments are correct.

Related issues, RFCs

Issue number: closes #1493

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my change is effective and works
• The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

• I have documented the migration process
• I have added, implemented necessary warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.